5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
- Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-7: Predefined Fields

Designer-Invoked Processes


The runtime application contains several predefined processes.  In general, these processes can be placed into two categories; processes that a designer can invoke, and processes that only APPX can invoke. Most of the predefined processes are only invoked by APPX.

Following is a list of the predefined processes that a designer can invoke (each of which is described in detail later in this chapter):

APPX MENU, which allows a user to select a new database and provides access to system administration, and application design.

BEGIN LIVE OPERATIONS, which transfers the run phase from initial setup or recovery processing to live operations.

CHECK GUI CLIENT, which determines if the current engine is connected to a GUI-enabled client.

DISPOSITION which allows a user to provide information that controls how and where a report is to print.

ENTER BILLING CODE, which allows a user to enter a value into the predefined field BILLING CODE.

GET CMD LINE PARM, which checks for the existence of a parameter on the command line used to invoke the current engine.

GET ENV VAR, which retrieves the contents of an environment variable.

GET FILE FROM CLIENT, which retrieves a file from the client system and stores it on the server.

PROCESS QUERY RECORD, which potentially adds a PCF record to the result set of a query.

SELECT DATABASE, which allows a user to select the appropriate database.

SEND FILE TO CLIENT, which retrieves a file from the server and stores it on the client system.

Application Design Manual                                         "Powered by Appx Software"

874

©2006 By APPX Software, Inc. All Rights Reserved